-
Notifications
You must be signed in to change notification settings - Fork 100
release: 3.4.8 #302
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
release: 3.4.8 #302
Conversation
|
🧪 Testing To try out this version of the SDK, run: Expires at: Thu, 26 Feb 2026 17:38:59 GMT |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No issues found across 30 files
Confidence score: 5/5
- Automated review surfaced no issues in the provided summaries.
- No files require special attention.
Architecture diagram
sequenceDiagram
participant User as Client Code
participant SDK as Stagehand SDK
participant API as Backend API
Note over User, API: 1. NEW: Binary/Streaming Request Support
User->>SDK: client.post(..., content=bytes_or_iter)
alt NEW: 'content' parameter usage
SDK->>SDK: Validate 'body' (JSON) is not set
SDK->>SDK: Pass raw content to underlying httpx transport
else Deprecated: 'body' with bytes
SDK->>SDK: Emit DeprecationWarning
SDK->>SDK: Treat as content
end
SDK->>API: POST /endpoint (Raw Binary Stream)
API-->>SDK: 200 OK
SDK-->>User: Response
Note over User, API: 2. UPDATED: Session Execution & Caching
User->>SDK: sessions.execute(..., should_cache=True)
SDK->>SDK: CHANGED: 'x-sent-at' header removed
SDK->>API: POST /v1/sessions/{id}/agentExecute
Note right of SDK: Payload includes {"shouldCache": true}
alt Success with Cache
API-->>SDK: 200 OK
Note left of API: Response includes 'cacheEntry' object
SDK-->>User: SessionExecuteResponse (w/ cache_entry)
else Standard Execution
API-->>SDK: 200 OK
SDK-->>User: SessionExecuteResponse
end
Note over User, API: 3. NEW: Session Replay
User->>SDK: sessions.replay(id)
SDK->>API: NEW: GET /v1/sessions/{id}/replay
API-->>SDK: 200 OK (JSON)
Note left of API: Returns actions, token usage, timestamps
SDK-->>User: SessionReplayResponse
shrey150
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pre-approving
pyproject.toml
Outdated
| [project] | ||
| name = "stagehand" | ||
| version = "3.4.7" | ||
| name = "stagehand-alpha" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this rename intentional?
| class DataCacheEntry(BaseModel): | ||
| cache_key: str = FieldInfo(alias="cacheKey") | ||
| """Opaque cache identifier computed from instruction, URL, options, and config""" | ||
|
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Checking that this caching functionality should be exposed right now
|
🤖 Release is at https://github.com/browserbase/stagehand-python/releases/tag/v3.4.8 🌻 |
Automated Release PR
3.4.8 (2026-01-27)
Full Changelog: v3.4.7...v3.4.8
Chores
This pull request is managed by Stainless's GitHub App.
The semver version number is based on included commit messages. Alternatively, you can manually set the version number in the title of this pull request.
For a better experience, it is recommended to use either rebase-merge or squash-merge when merging this pull request.
🔗 Stainless website
📚 Read the docs
🙋 Reach out for help or questions
Summary by cubic
Release 3.4.8 adds session replay and per-execute caching, simplifies session params, and adds raw binary/streaming request support. It also refreshes CI workflows.
New Features
Migration
Written for commit 7914f28. Summary will update on new commits. Review in cubic